home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 24
/
Aminet 24 (1998)(GTI - Schatztruhe)[!][Apr 1998].iso
/
Aminet
/
comm
/
mail
/
AEMail.lha
/
aemail143
/
files.lha
/
email.txt
< prev
next >
Wrap
Text File
|
1997-08-31
|
20KB
|
350 lines
Understanding email
by John F. Zacharias
(c) 1997 by John F. Zacharias, All Rights Reserved
One of the most popular uses of the Internet is it's ability to transmit
mail anywhere in the world. Transmission is virtually instantaneous which
beats the more commonly used U.S. Postal Service in which mail is often
referred to as "smail" or "snail mail" because of the long time it takes to
receive letters, especially from foreign sources . Mail on the Internet is
referred to as "email" or "electronic mail" because it uses electronic
means to transfer the mail that is very fast.
To understand email you need to understand a few concepts and the
terminology of the Internet. First of all you need to understand the
"client/server" concept. A "client" is a program on your computer which
talks to a "server" (one that provides a service) program which is
generally on another computer. It is the "server" which actually talks to
the Internet and provides various Internet services such as the ability to
transfer email, files, world wide web pages, etc. throughout the world of
the Internet.
The "client" programs on your computer generally handles a single function
such as processing mail, transferring files, or reading world wide web
pages. In this article I will occasional make reference to my email client
program, AEMail, and relate some of the concepts to it.
To talk to the "server" program, you need something called a TCP/IP stack.
TCP/IP stands for "Transmission Control Protocol/ Internet Protocol". The
word "protocol", which you will see a lot with the Internet, is defined as
"a clearly defined set of rules by which two sides communicate" and is a
widely used term in the telecommunications arena. For the Internet these
"protocols" are generally published as RFC's, or "Request for Comments".
Each RFC is numbered and describes the current accepted "protocol" for a
particular area.
The term "stack" refers to a special model that is used for describing
telecommunications. This is a fairly lengthy concept that we will not go
into here. The TCP/IP stack is provided by a special kind of
communication's program that resides on your computer. Three widely used
TCP/IP stacks that are used on the Amiga are AmiTCP, Termite TCP, and
Miami. Of these three programs AmiTCP is probably the hardest to use and
Miami is probably the easiest.
The "server" program is general provided by an ISP, or "Internet Service
Provider". Since the "client" and "server" programs talk with commonly
known "protocols", each program can reside of any computer whether it be a
PC, Macintosh, Amiga, or a Unix based computer. As long as a particular
ISP supports the particular protocol that is being used, your Amiga can
talk to it. If you hear "we don't support the Amiga" from an ISP it only
means that they do not have anyone on their staff that knows anything about
the Amiga so they can not provide any assistance if you are having trouble
connecting to them. If you can talk to them in Internet specific terms,
then they should be able to answer your questions. In other words, don't
mention that you have an Amiga!
There is one other thing you need to know about the connection to your ISP.
There are three ways a home computer can talk to the ISP. These are
generally referred to as shell, SLIP, or PPP accounts. With a "shell"
account your computer does not have to know TCP/IP. It can communicate
with the ISP with a simple terminal program. However, in this case you
computer is nothing more than a "dumb terminal". The "client" programs
actually reside on the ISP. In this case you are limited in what you can
do and you need to know Unix, since most ISP shell accounts use a Unix
operating system interface.
Both PPP and SLIP can talk TCP/IP to your ISP which means that client
programs, such as email programs, web browsers, or file transfer programs
can reside on your Amiga. PPP stands for "Point-to-Point Protocol" and
SLIP stands for "Serial Line Internet Protocol". SLIP is an older protocol
and is not as reliable as PPP. Most systems today use PPP. Both of these
protocols allow you to dial up your ISP and then talk using TCP/IP.
The Internet is a global communication facility that talks to many
locations at once. It is similar to the Postal Service in that you can
deposit your mail at any one location and it will be reliably delivered to
it's destination provided you have addressed it correctly.
Like mailing a letter, you need to have an address so that the Internet
knows where to deliver it. Addresses on the Internet are a series of
numbers referred to as an IP address. These numbers can identify a
location just as the city, state, and zip code on a letter can identify the
post office that a letter is to be delivered to.
Since IP addresses are nothing more than numbers they are very hard to
remember. So the Internet has come up with something called a "domain"
name. The domain is a name that your ISP has assigned to itself. There
are certain rules that have to be followed for this name. First of all the
name can not be used by someone else. In the US, you will usually see the
domain name followed with a suffix like .com, .edu., or .org (which stand
for commercial organization, educational organization, or non-profit
organization). In foreign countries the domain name generally has a suffix
which identifies the country (i.e., .uk, .fr, .dk, .de, etc.).
The Internet itself can only identify locations with the numeric IP
address. However, each ISP has a "domain name service" (DNS) which can
look up a domain name and get it's corresponding IP address. This means
you can use domain names in addresses and not worry about what the real IP
address is. When you set up your TCP/IP stack software you may have to
give the IP addresses of your ISP's Domain Name Servers. However smarter
TCP/IP software (such as Miami) can get these DNS IP addresses
automatically.
In order to receive email you will have an "email address". This email
address looks like this: username@domain-name. The domain-name is
generally the domain name of your ISP. Sometimes this domain name is
prepended with a computer name followed by a period; however, just the
domain name of the ISP usually is sufficient. The username is a name
either chosen by you or assigned to you by your ISP. This is how the ISP
identifies you. You should check with you ISP to be sure what your email
address is.
When you send mail to someone you must know their email address also. This
is how you address your "letters" to them just as the address on the
letters you send by snail mail are addressed to a particular recipient.
You can think of the part of the email address to the left of the "@" sign
as the same as your street address or P.O. Box and the part to the address
to the right if the "@" as the city, state, and zip code which identifies
the post office (ISP) that handles your mail. You can also specify a "real
name" which can be thought of as the name part of your address. The real
name is placed either after the email address surrounded by parenthesis or
in front of the email address with the email address surrounded by less
than/greater than brackets (<......>). You do not need a real name to
receive email, however. The email address is sufficient. AEMail uses the
real-name <email address> format in identifying who is sending the mail.
With the Internet there are two protocols that handle sending and receiving
mail. These are the SMTP (Simple Mail Transfer Protocol) and the POP or
Post Office Protocol. Mail is sent using the SMTP protocol. This is also
the protocol that the Internet uses for transferring mail between two
different locations. The POP protocol is used to transfer the mail from
your ISP to your client software. With the POP protocol your ISP is able
to store your mail in mailboxes on the ISP's computer until you are ready
to retrieve it. That is why you use the SMTP protocol to send mail and the
POP protocol to receive mail.
Your ISP may have two different servers to handle mail, the SMTP server to